As part of this article, it is assumed that the Sametime 8.5.1 Embedded Client has already been installed into your Lotus Notes 8.5.1 Client that has had Fixpack 4 applied as per the Sametime Documentation recommended system requirements. (Lotus Notes 8.5.1 & 8.5.2 do NOT ship with the Embedded Sametime 8.5.x client – they ship with the 8.0.2 Sametime embedded client)

Cisco Phone Control and Presence 8.0 Plug-in

Here is a link to the Integration Note for the Deploying of the Cisco Phone Control and Presence 8.0 with IBM Lotus Sametime:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucibmlotus/cpcap/8x/english/integration/guide/cpcapig.html#wp64653

Follow the instructions in this document for the configuring of the update site.  

However, when you read the section: 

2. How to Set Up the Plug-in Update Site, there is a Note that states:

If Cisco Unified Messaging with IBM Lotus Sametime is also being deployed, copy all the .jar files from the UpdateSite/plugins and UpdateSite/features directories of that package to the respective directories in this package. This creates a combined update site so that the plug-ins can be configured together.

What I have learnt from previous implementations is DO NOT DO THIS as it does not work.  If you have a combined Update Site, then the Unified Messaging Plug-In, will not install and constantly errors.  You must create separate Update Sites.
 

Cisco Unified Messaging 8.0 Plug-In

Here is a link to the Release Notes for Cisco Unified Messaging 8.0 with IBM Lotus Sametime:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucibmlotus/unifiedmsg/8x/release/notes/801cumstrn.html
 
Follow the instructions in this document for the configuring of the update site. 

Create an Eclipse Update Site

If you already have Eclipse update site in your Domino environment, you can skip this step.

The easiest way to create an Eclipse Update Site is to use Notes 8.x Eclipse Update Site template.
 
Go to File - Application - New, enter the required data, and check the Show advanced templates check-box. Be sure you selected your server for template list. Select the Eclipse update site and click OK. When the process finishes, you will have your eclipse update site.

Create a Widget catalog database

Again, if you already have a widget catalog database in your Domino environment, you do not need to read this.

The easiest was to create a Widget Catalog is to use Notes 8.x Widget Catalog template.

Go to File - Application - New, enter the required data, and check the Show advanced templates check-box. Be sure you selected your server for template list. Select the Widget Catalog and click OK.

When the process finishes, you will have your widget catalog.

Importing the Plug-In Update Site

Now that you have your locally saved, configured plug-in updatesite files along with your eclipse update site and widget catalog on your Domino server, you can proceed with deployment.

What you need to do now is to import your plug-in to your eclipse update site database. This is a simple step.

Open your Eclipse Update Site database and click on the Import local update site action button. A dialog pops up. All you need to do is to point the location of the updatesite folder of the configured plug-in and select the site.xml file on your hard drive and select OK. If all goes well, you should have an update site imported in about a minute or so.

You will need to repeat this process for each update site that you want to import.

You should see something like this:

Creating a widget for your plug-in

To deploy a plug-in for the integrated Lotus Notes with embedded Sametime client, you need to create a widget from your update site.

You will have to manually create your own extension.xml file that you will attach to the Widget. It was my experience that attempting to use the “wizards” does NOT generate a correctly formed extension.xml file whereas manually created ones work.

You can name the file whatever you want, as long as it has the correct format. Below is the content of my extension file used for the Cisco Phone Control and Presence Plug-In (attributes marked bold are changeable).

 <?xml version="1.0" encoding="UTF-8"?> 

<webcontextConfiguration version="1.1">

<palleteItem id="com.cisco.sametime.phone.featurest800" imageUrl=""

providerId="com.ibm.rcp.toolbox.prov.provider.ToolboxProvisioning"

title="Cisco Phone Control and Presence"

url="nrpc://myupdatesiteserver.com/__482577b9000551b5/site.xml">

<preferences>

</preferences>

<data>

<installManifest>

<![CDATA[

<install>

<installfeature description="Cisco Phone Control and Presence"

id="com.cisco.sametime.phone.featurest800"

name="Cisco Phone Control and Presence"

required="true">

 <requirements>

  <feature id="com.cisco.sametime.phone.featurest800" version="8.0.1.1094"/>

 </requirements>

</installfeature>
</install>

]]>
</installManifest>

</data>

</palleteItem>

</webcontextConfiguration>

• PalleteItem id, InstallFeature and Feature id must be the same as ID of the plug-in in the update site.
• PalleteItem title, InstallFeature, description and name are totally up to you 
• Feature id version must correspond to the value of the field Version in the update site document. 
• URL - I have found that you must use the nrpc format (for some reason http doesn’t appear to work). The link can be obtained by going to the actions menu of your eclipse update site database and select Show URL’s

Go to your widget catalog database, click the “Create New widget” action button.

Type in the name of your widget and a description.

Make sure that you specify a category for your widget and then attach the created extension.xml file.

Save the document and you should have a widget, ready to deploy.

If you are deploying the Cisco Phone Control and Presence Plug-In, you will need to create 2 widgets (along with a separate extension.xml file for each) in order for these features to be implemented.  One widget for the Cisco Phone Control and Presence with Lotus Sametime and one for the Cisco JTAPI for Phone Control and Presence with Lotus Sametime.

The other item that you will need to implement in order to have the Cisco Phone Presence status update correctly is a desktop policy setting through your Lotus Notes Administrator Client.

Create a Managed Setting to update the plugin_customization.ini file

As part of the Cisco Phone Control and Presence Plug-In configuration there is a section in the documentation that refers to Enabling Phone Status for IBM Lotus Sametime 8.5.1

In this section, there is a managed-settings.xml file created and saved into the root directory of the updatesite.  What this file is supposed to do is update a setting in the user’s local C:\IBM\Lotus\Notes\framework\rcp\plugin_customization.ini file to read:

com.ibm.collaboration.realtime/enableExtendedStatus=true

In order to have this setting updated automatically rather than manually edit the file in your users Lotus Notes client when using the Integrated Lotus Notes with Embedded Sametime 8.5.1 Client, you need to create or modify a Desktop Policy setting using your Lotus Notes Administrator Client as follows:

• Open your Lotus Notes Administrator Client 
• Select File - Open Server - Select your server 
• Click on the Person & Groups tab - select settings 
• If you already have Desktop Setting document, select the one that you want to modify.  If you don’t have a Desktop Policy Setting document, click on the Add Setting button and select Desktop. 
• With your Desktop Setting document in edit mode, use the scroll buttons at the top of the screen, until you see the Custom Settings tab

• Now click on the Managed Settings tab and click Edit list 
• In the dialog box enter the following:

• Click on the Add/Modify Value and then click OK.
• You should now see this entry:

As long as this Desktop Setting is part of one of your Policies, then whoever that policy has been applied to will have this setting applied to their Lotus Notes Client, next time they authenticate with the server.

Please Note: this does not actually change the entry in the plugin_customization.ini file as the change is applied directly to the Lotus Notes Client which overrides the setting in the plugin_customization.ini file.

Deploy the Plug-In Automatically

With the widgets created, it is time to deploy them. The good news is that you can do this automatically via the Lotus Notes Desktop settings document in a Policy.

We will need to modify the Desktop Setting document.

With your Desktop Setting document in edit mode, use the scroll buttons at the top of the screen, until you see the Widgets tab

There you specify your server name and category of widgets you want users to install.

If you don’t specify a category the plug-in will not be deployed automatically.

You can save other defaults or change them, but beware that disallowing people to display My Widgets sidebar will cause you issues later on with users that didn’t get the plug-in automatically installed.

Save the setting document, include it in your Policy and deploy it.

Manually installing the plug-in

Despite all your best efforts to automate the process, you may still have to do this for some users.

• Go to File - Preferences - Widgets, 
• Select Show widget toolbar and the “my widgets” sidebar panel and click OK. 
• My widgets sidebar should now appear on the right. 
• Right click on it and select Catalog - Update. 
• This will force an update of user’s local widget catalog (which is created automatically) and thus trigger plug-in installation.

User input

When installing the plug-in, you will receive a notification about your intention to install the plug-in.

Note that the default option is Do Not Install

Once the plug-in has installed, the user will have to restart their Lotus Notes client for changes to take effect.